- oXygen-user - www.oxygenxml.com

Antenna House configuration file
by KAATMAN Matthew 06 Aug '13

06 Aug '13

Hey Guys, How can I specify a configuration file for Antenna House to use? I have one option that fixes our page numbering. Can I point to this config through Oxygen? <formatter-config> <pdf-settings page-labels="false" /> </formatter-config> Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 1

Error in Oxygen XML editor version 15 during validation
by Ananth Narayanan 02 Aug '13

02 Aug '13

Dear All, Could any one help me on how to resolve the error, I pasted the error as an XML file below. I am validating the XML file using rules.sch file. -------------------- <?xml version="1.0" encoding="UTF-8"?> <report xmlns="http://www.oxygenxml.com/ns/report"> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>error</severity> <description>Failed to compile stylesheet. 4 errors detected.</description> <systemID>C:\DATA\Rule-based validation\rules.sch</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>fatal</severity> <description>The filtered expression in an XSLT 2.0 pattern must be a simple step</description> <systemID>C:\DATA\Rule-based validation\rules.sch</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>fatal</severity> <description>The filtered expression in an XSLT 2.0 pattern must be a simple step</description> <systemID>C:\DATA\Rule-based validation\rules.sch</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>fatal</severity> <description>The filtered expression in an XSLT 2.0 pattern must be a simple step</description> <systemID>C:\DATA\Rule-based validation\rules.sch</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>fatal</severity> <description>The filtered expression in an XSLT 2.0 pattern must be a simple step</description> <systemID>C:\DATA\Rule-based validation\rules.sch</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> <incident> <engine>ISO Schematron (XSLT 2.0)</engine> <severity>fatal</severity> <description>Got a fatal error trying to create a transformer from the stylesheet!</description> <systemID>C:\DATA\sample.xml</systemID> <operationDescription> <mainValidationFile>C:\DATA\sample.xml</mainValidationFile> </operationDescription> </incident> </report> ------------- Regards Anantha

2 1

Click URI in results from a xquery to open in Oxygen?
by Steven Anderson 02 Aug '13

02 Aug '13

Sometimes I run an xquery to find certain patterns in groups of files (for example, a section element without a title element) and I'd like to be able to double-click on the result from the query to open it up in Oxygen. Is something like that possible? Right now I'm seeing a sequence tab open that has my results (the results are file URIs), but the results are clickable. -- Steve

2 1

Re: [oXygen-user] Feature request: Validation for linked images in SVG paths
by Wendell Piez 31 Jul '13

31 Jul '13

Matt, Oops, sorry about that $t, it was a relic of an earlier iteration. It should be . (dot). I just started with Alex's code, reworked and reworked again. (Compulsive activity after a long day of XSLT/XQuery/XPath.) There is certain to be other tuning necessary for your case. Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ On Tue, Jul 30, 2013 at 11:36 PM, KAATMAN Matthew < matthew.kaatman(a)biomerieux.com> wrote: > Hey Wendell,**** > > ** ** > > I am learning from all these examples. $t is undefined. Would you mind > clarifying what it should be set to?**** > > ** ** > > Thanks! > Matt**** > > ** ** > > *From:* oxygen-user-bounces(a)oxygenxml.com [mailto: > oxygen-user-bounces(a)oxygenxml.com] *On Behalf Of *Wendell Piez > *Sent:* Tuesday, July 30, 2013 6:20 PM > > *To:* oxygen-user(a)oxygenxml.com > *Subject:* Re: [oXygen-user] Feature request: Validation for linked > images in SVG paths**** > > ** ** > > Hi,**** > > ** ** > > Schematron is not only useful; it's fun. (I admit I am hard-core.)**** > > ** ** > > Refactoring a little (but untested):**** > > ** ** > > <let name="referencedImages" > value="$svgDocument//*:image/@*:href[not(starts-with(.,'data'))]"/>**** > > <let name="missingImages" > value="$referencedImages[not(exslt:exists(resolve-uri($t, > base-uri($svgDocument))))]"/>**** > > <assert test="empty($missingImages)">An image file referenced in SVG image > <value-of select="@href"/> is missing:**** > > check for <value-of select="string-join($missingImages,', ')"/></assert> > **** > > ** ** > > Thanks to Alex for doing the real work.**** > > ** ** > > Cheers, Wendell**** > > ** ** > > > **** > > Wendell Piez | http://www.wendellpiez.com > XML | XSLT | electronic publishing > Eat Your Vegetables > _____oo_________o_o___ooooo____ooooooo_^**** > > ** ** > > On Tue, Jul 30, 2013 at 10:35 AM, Alex Jitianu <alex_jitianu(a)sync.ro> > wrote:**** > > Hello Matt, > > 1. The odd line is related to the fact that when validating with a > Schematron file under the hood the Schematron is transformed in XSLT and > that XSLT is applied on the document. The reported error line is inside > that intermediate XSLT and unfortunately I don't think there is a round > trip to get the real location in the Schematron file. > > 2. I believe the NullPointerException is a side effect of the fact that I > didn't consider the fact that the SVG file is also referred relatively in > the DITA document. As a result the SVG will not get located and parsed by > the document() function and later on exists() function will break. In the > example below I've added the resolve-uri() function to compute the SVG > document location. > > 3. In the example below I've changed a bit the assert XPath to ignore the > href values that start with 'data'. You should also take into account the > fact that the SVG can contain multiple image elements. Perhaps you could > assert it more elegantly than this but here a possible solution:**** > > > > <schema > xmlns="http://purl.oclc.org/dsdl/schematron"<http://purl.oclc.org/dsdl/schematron> > queryBinding="xslt2" > xmlns:exslt="http://expath.org/ns/file" <http://expath.org/ns/file>> > <ns uri="http://expath.org/ns/file" <http://expath.org/ns/file>prefix="exslt"/> > <pattern> > <rule context="image">**** > > <let name="svgDocument" value="document(resolve-uri(@href, > base-uri()))" /> > <let name="svgExists" value="exists($svgDocument)"/> > <assert test="$svgExists">The SVG file can't be loaded > <value-of select="resolve-uri(@href, base-uri())"/></assert> > > <let name="realImages" value="$svgDocument//*:image/@*:href"/> >  > <let name="testImages" value="for $realImage in $realImages > return if (not($svgExists) or starts-with($realImage, 'data')) then true() > else exslt:exists(resolve-uri($realImage, base-uri($svgDocument)))"/> > <assert test="empty(index-of($testImages, false()))">The image > file must exist</assert>**** > > > > </rule> > </pattern> > </schema> > > Best regards, > Alex**** > > On 30-Jul-13 3:33 PM, KAATMAN Matthew wrote:**** > > Hey Alex,**** > > **** > > This looks really promising!**** > > **** > > When I run validate with this schematron I get the following:**** > > **** > > System ID: C:\svn\scripts\svgCheck.sch**** > > Engine name: ISO Schematron (XSLT 2.0)**** > > Severity: fatal**** > > Type: XML validation**** > > Start location: 149:0 (Odd because the schematron is only 14 lines)**** > > **** > > System ID: C:\dita\pt\products\vitek2systems\pi\Appendix_A.dita (This is > the first file with an SVG for the document I checked.)**** > > Engine name: ISO Schematron (XSLT 2.0)**** > > Severity: error**** > > Description: Exception thrown by extension function {public static boolean > com.saxonica.functions.extfn.EXPathFile.exists(java.lang.String)}: > java.lang.NullPointerException**** > > Type: XML validation**** > > **** > > Even if I delete all SVG references, I receive the above two errors.**** > > **** > > I then tried it on a map with more SVGs and some that were verified to be > broken. It is properly detecting the errors but I see false positives when > the SVG contains embedded images instead of linked. I believe it’s trying > to verify the binary data as the uri.**** > > **** > > System ID: C:\dita\en\products\simon\service\Attachments.dita**** > > Engine name: ISO Schematron (XSLT 2.0)**** > > Severity: error**** > > Description: A sequence of more than one item is not allowed as the first > argument of resolve-uri() ("data:image/jpeg;base64,/9j/4AA...", > "data:image/png;base64,iVBORw0K...") **** > > Type: XML validation**** > > **** > > Is there a way for me to adjust the schematron to ignore href values that > start with “data”?**** > > **** > > I had previously attended a webinar Oxygen presented on schematron. I’m > finally starting to understand how powerful it can be!**** > > **** > > Thank you, > Matt**** > > **** > > **** > > *From:* oxygen-user-bounces(a)oxygenxml.com [ > mailto:oxygen-user-bounces@oxygenxml.com<oxygen-user-bounces(a)oxygenxml.com>] > *On Behalf Of *Alex Jitianu > *Sent:* Tuesday, July 30, 2013 2:25 AM > *To:* oxygen-user(a)oxygenxml.com > *Subject:* Re: [oXygen-user] Feature request: Validation for linked > images in SVG paths**** > > **** > > Hello Matt, > > In Oxygen v15.0 we've added in the "Validate and check for Completeness" > dialog a new entry called "Additional schematron checks" in which you can > specify additional Schematron checks that should be be executed on the > topics. You can perform the check you've described using a Schematron file > with the following content: > > <?xml version="1.0" encoding="UTF-8"?> > <schema > xmlns="http://purl.oclc.org/dsdl/schematron"<http://purl.oclc.org/dsdl/schematron> > queryBinding="xslt2" > xmlns:exslt="http://expath.org/ns/file" <http://expath.org/ns/file>> > <ns uri="http://expath.org/ns/file" <http://expath.org/ns/file>prefix="exslt"/> > <pattern> > <rule context="image[ends-with(@href, '.svg')]"<image[ends-with%28(a)href,%27.svg%27%29]> > > > <let name="svgDocument" value="document(@href)" /> > <assert > test="exslt:exists(resolve-uri($svgDocument//*:image/@*:href, > base-uri($svgDocument)))"> > The image file from the following SVG doesn't exist: > <value-of select="base-uri($svgDocument)"/></assert> > </rule> > </pattern> > </schema> > > Best regards, > Alex > -- > Alex Jitianu > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > > On 29-Jul-13 9:38 PM, KAATMAN Matthew wrote:**** > > Hey Guys,**** > > **** > > This is a feature request that's not extremely crucial, but it would be > helpful for us.**** > > **** > > I'm having our authors create SVG overlays and link to the background > image (jpeg or png).**** > > **** > > Sometimes they accidentally link to an image that isn't in our repository > path.**** > > **** > > Within the SVG, I'll end up with something like:**** > > <image width="1200" height="1807" > xlink:href="../../../../../../../Users/Username/Pictures/PREVI > PAV/PAV_printer_cover_open.jpg" >**** > > **** > > When it should be:**** > > <image width="1200" height="1807" > xlink:href="images/PAV_printer_cover_open.jpg" >**** > > **** > > Although, the validate/check for completeness wouldn't catch this on their > workstation as the image exists and is valid, it would find it quickly on > mine since it's outside the path that gets checked in and I’d be missing > that image.**** > > **** > > It doesn't seem like the OT throws any errors either. The only way I find > out is when I'm viewing the PDF and notice that antenna house has > substituted a broken image.**** > > **** > > Example:**** > > **** > > **** > > Thanks! > Matt**** > > AVIS : Ce courrier et ses pieces jointes sont destines a leur seul > destinataire et peuvent contenir des informations confidentielles > appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes > informe que toute lecture, divulgation, ou reproduction de ce message et > des pieces jointes est strictement interdite. Si vous avez recu ce message > par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que > ses pieces jointes. NOTICE: This message and attachments are intended only > for the use of their addressee and may contain confidential information > belonging to bioMerieux. If you are not the intended recipient, you are > hereby notified that any reading, dissemination, distribution, or copying > of this message, or any attachment, is strictly prohibited. If you have > received this message in error, please notify the original sender > immediately and delete this message, along with any attachments. > > **** > > _______________________________________________**** > > oXygen-user mailing list**** > > oXygen-user(a)oxygenxml.com**** > > http://www.oxygenxml.com/mailman/listinfo/oxygen-user**** > > **** > > AVIS : Ce courrier et ses pieces jointes sont destines a leur seul > destinataire et peuvent contenir des informations confidentielles > appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes > informe que toute lecture, divulgation, ou reproduction de ce message et > des pieces jointes est strictement interdite. Si vous avez recu ce message > par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que > ses pieces jointes. NOTICE: This message and attachments are intended only > for the use of their addressee and may contain confidential information > belonging to bioMerieux. If you are not the intended recipient, you are > hereby notified that any reading, dissemination, distribution, or copying > of this message, or any attachment, is strictly prohibited. If you have > received this message in error, please notify the original sender > immediately and delete this message, along with any attachments. **** > > ** ** > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user**** > > ** ** > AVIS : Ce courrier et ses pieces jointes sont destines a leur seul > destinataire et peuvent contenir des informations confidentielles > appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes > informe que toute lecture, divulgation, ou reproduction de ce message et > des pieces jointes est strictement interdite. Si vous avez recu ce message > par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que > ses pieces jointes. NOTICE: This message and attachments are intended only > for the use of their addressee and may contain confidential information > belonging to bioMerieux. If you are not the intended recipient, you are > hereby notified that any reading, dissemination, distribution, or copying > of this message, or any attachment, is strictly prohibited. If you have > received this message in error, please notify the original sender > immediately and delete this message, along with any attachments. >

2 1

Feature request: Validation for linked images in SVG paths
by KAATMAN Matthew 31 Jul '13

31 Jul '13

Hey Guys, This is a feature request that's not extremely crucial, but it would be helpful for us. I'm having our authors create SVG overlays and link to the background image (jpeg or png). Sometimes they accidentally link to an image that isn't in our repository path. Within the SVG, I'll end up with something like: <image width="1200" height="1807" xlink:href="../../../../../../../Users/Username/Pictures/PREVI PAV/PAV_printer_cover_open.jpg" > When it should be: <image width="1200" height="1807" xlink:href="images/PAV_printer_cover_open.jpg" > Although, the validate/check for completeness wouldn't catch this on their workstation as the image exists and is valid, it would find it quickly on mine since it's outside the path that gets checked in and I'd be missing that image. It doesn't seem like the OT throws any errors either. The only way I find out is when I'm viewing the PDF and notice that antenna house has substituted a broken image. Example: [cid:image001.png@01CE8C60.F936CBB0] Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

3 6

XHTML to DITA topic: transformation failed
by Yves Barbion 25 Jul '13

25 Jul '13

Hi group I've got a simple HTML page written in oXygen XML Author 15. When I try the XHTML to DITA topic transformation scenario, it fails: System ID: C:\temp\oxygen_blogpost.html Scenario: XHTML to DITA topic XML file: C:\temp\oxygen_blogpost.html XSL file: C:\Program Files\Oxygen XML Editor 15\frameworks\dita\DITA-OT\demo\h2d\preprocess.xsl Document type: XHTML Engine name: Saxon6.5.5 Severity: error Description: C:\Program Files\Oxygen XML Editor 15\frameworks\dita\DITA-OT\demo\h2d\preprocess.xsl (The system cannot find the path specified) Any ideas? -- Yves Barbion www.scripto.nu

2 1

Transformation Log
by KAATMAN Matthew 18 Jul '13

18 Jul '13

I know this was recently discussed, but I'm searching my email and can't find it. Where is the option to turn the (DITA content) transformation log back on? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 2

Oxygen not loading images in Author mode
by Holley, Erik 18 Jul '13

18 Jul '13

Oxygen Author 14.2 is showing a "can't display image" in Author mode. First test was setting an image in the framework's CSS file: content: oxy_url(.....) This test fails with web, http://, images, but works with local, file://, images. Second test was creating an XHTML file, adding an <img> element and setting the src attribute to a web address. Same failure. It seems Oxygen is having trouble retrieving images from http:// addresses. And, this only occurs on my client's machine. My machine works correctly. The client has web access, as we performed troubleshooting over WebEx. What could make this happen?

2 1

[Ann] New maintenance build available for oXygen 15.0 (2013071613)
by Oxygen XML Editor Support 18 Jul '13

18 Jul '13

Dear oXygen users, We announce the release of a new maintenance build (2013071613) for oXygen 15.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2013071613 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Automatic re-indexing on file changes or ...?
by Steven Anderson 18 Jul '13

18 Jul '13

Working with large filesets with frequent changes, reindexing for resource searching can be a pain. I have to remember to do it and it takes a while. Is there a way that oxygen can automatically update the index when files change? Alternatively, is there a command-line option to rebuild the index that I can integrate with my workflow? -- Steve

2 3