- oXygen-user - www.oxygenxml.com

Feature request: wildcards or regex in directory filter
by KAATMAN Matthew 26 Aug '13

26 Aug '13

I don't know how feasible this is, but a feature that I have never seen in any editor is the ability to use a wildcard or regex in the directory path filter for functions such as search/replace and open files. Imagine in the "Find/Replace in Files->Specified Path" if I could specify something like: C:\dita\*\products\testproduct\user Where my directory structure contained a list of country codes where the * would go. I've been writing scripts to accommodate these kind of actions. The same functionality would be useful for opening files also. I often want to open a map and all of the translations of that map across many directories. C:\dita\*\products\testproduct\user\testmap.ditamap I'm curious how difficult something like that would be. 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

Print/save report from Diff Directories?
by David Sewell 22 Aug '13

22 Aug '13

Is there any way to print or save the output of a Diff Directories listing? I have a use case where it would be very helpful to do so, but I do not see any menu or contextual options with this function. David -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: dsewell(a)virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/

2 2

Git-aware XML Diff Support?
by Eliot Kimber 22 Aug '13

22 Aug '13

I've started using Git for version control wherever possible. Looking at the help, it looks like there is support for SVN version diffing, but nothing for Git. Have you considered providing at least Git-aware differencing, if not a full Git client analogous to the SVN client? Cheers, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

3 3

Publish DITA topic or HTML page to Wordpress blog
by Yves Barbion 16 Aug '13

16 Aug '13

Hi group Is there a way to write a blog post in oXygen XML Author and then publish that post on a Wordpress site, similar to what can be done in Word? http://wpmu.org/how-to-use-microsoft-word-to-publish-directly-to-your-wordp… It would be nice if this could be done with a generic DITA topic, but a simple HTML page would be OK too. Thanks -- Yves Barbion www.scripto.nu

2 1

Feature request: Search character map by name
by KAATMAN Matthew 08 Aug '13

08 Aug '13

Would it be possible to add a by "name" option for the character search? Maybe something like this: http://i.imgur.com/VFNsA3P.png Where you could search for "En" and bring up "En Dash" for 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.

2 1

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