- oXygen-user - www.oxygenxml.com

Re: [oXygen-user] Pretty Print <lb/> in Oxygen
by Syd Bauman 12 Jan '16

12 Jan '16

A few hours ago Ute Recker-Hamm posted a wonderful question to TEI-L, the main list for the Text Encoding Initiative.[1] She basically asked "what do y'all do to get your physical lines, as encoded with the empty TEI <lb> element, to line up nicely in oXygen?". I remember asking a similar question a few years ago, and vaguely recall being told that manipulating the options under "Preferences > Editor / Format / XML" (in particular the "Preserve space" and "Default space" lists) should get format-and-indent to do the trick. However, I recall that I never got it working to my satisfaction, and when I look through the archives of this list now, I can't find the answer I recall. So what is "it" that I want format-and-indent to do? When given a text that looks like this: view A ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. I'd like it to end up formatted as it is now -- with each <lb> starting a new line. If the desired line length were long enough, it wouldn't be changed at all. If the desired line length were shorter, it might look like this: view B ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. What I *don't* want is for format-and-indent to make it look like this: view C ---- - I call our world Flatland, not because we call it so, but to make <lb/>its nature clearer to you, my happy readers, who are privileged to live <lb/>in Space. Imagine a vast sheet of paper on which straight Lines, Triangles, <lb/>Squares, Pentagons, Hexagons, and other figures, instead of remaining <lb/>fixed in their places, move freely about, on or in the surface, but without <lb/>the power of rising above or sinking below it, very much like shadows <lb/>—only hard with luminous edges—and you will then have a pretty <lb/>correct notion of my country and countrymen. Alas, a few years ago, <lb/>I should have said “my universe:” but now my mind has been opened <lb/>to higher views of things. In fact, if I had my druthers, an input document that looked like view C would come out of the processing looking like view A or B. Note ---- [1] Those of you who are members of a TEI list at Brown can find it at https://listserv.brown.edu/?A2=ind1410&L=tei-l&F=&S=&P=64155. I have not re-produced it here because I did not get the original poster's permission to do so. (Not that I think it is illegal or immoral to re-post without such permission, only that it's rude.)

7 9

Not indent elements with 'linefeed-treatment="preserve"'?
by Tony Graham 12 Jan '16

12 Jan '16

Is there a way that a framework can make oXygen not reindent elements that have 'linefeed-treatment="preserve"'? http://www.oxygenxml.com/doc/versions/17.0/ug-editor/#topics/preferences-ed… says that elements can be added to the 'Preserve space' list, but "*[@linefeed-treatment='preserve']" isn't a 'simple node test' and seems to be being silently ignored. Even if it did work, it can't be set by the 'focheck' framework. (Separately, the ability to edit an item in the list, rather than having to make a new item based on an existing item then deleting the old item, seems to me to be useful.) http://www.oxygenxml.com/doc/versions/17.0/ug-editor/#topics/format-and-ind… says that it can be done with CSS using 'white-space: pre', but *[linefeed-treatment=preserve] { white-space: pre; } is having no effect on Text mode 'Format and Indent Element' results. (Separately again, is there a key combination to insert a line break that doesn't also insert indenting white-space?) Regards, Tony Graham. -- Senior Architect XML Division Antenna House, Inc. ---- Skerries, Ireland tgraham(a)antenna.co.jp

3 2

oXygen to WordPress
by Ben McGinnes 12 Jan '16

12 Jan '16

Hello, So I stumbled across this post from a couple of years ago: https://www.oxygenxml.com/pipermail/oxygen-user/2013-August/004754.html Basically just asking for a feature to update a WordPress blog and said request being forwarded along. I've got two questions: 1) Did it become a feature? 2) If not, now that WordPress supplies an optional JSON based REST API, could the request be revisited since it ought to make it easier to make the two things play nicely together? WordPress API documentation: http://v2.wp-api.org/ I've only looked at it briefly, but it's REST so it can't be that hard, not as far as communicating with the server is concerned, at any rate. I've done a few client-side interaction things like this at times; mainly grabbing Bitcoin and/or currency live data and playing with the Twitter API so from my perspective the worst case scenario is making the right HTML template to play nicely at the other end and adding a few Python scripts (well, of course, by now everyone saw *that* language preference coming). Still, there's a lot to be said for "point and click" if it just works. Although the Github repositories also include command line tools and a console for the thing, so chances are integration could be reduced to calling the relevant commands to do whatever. The rough edges at the moment appear to be limited to generating the OAuth credentials, but that's not a huge chore for most WordPress admins. Regards, Ben -- Ben McGinnes http://www.adversary.org/ Twitter: benmcginnes Writer, Systems Administrator, Trainer, ICT Consultant GPGME Python 3 API Maintainer, GNU Privacy Guard https://www.gnupg.org/ Encrypted email preferred, primary OpenPGP/GPG key: 0x321E4E2373590E5D OpenPGP/GPG key here: http://goo.gl/GVGwT and http://goo.gl/SDs0D OpenPGP/GPG key transition: http://www.adversary.org/keyswitch.txt.asc

3 9

Re: [oXygen-user] XSLT Processor under XProc
by George Bina 11 Jan '16

11 Jan '16

Dear David, You can find the engine used when running XProc scripts with Calabash simply by invoking a stylesheet from XProc that outputs the processor name and version, like the one below: <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0"> <p:input port="source"> <p:inline> <doc>Hello world!</doc> </p:inline> </p:input> <p:output port="result"/> <p:xslt> <p:input port="parameters"> <p:empty/> </p:input> <p:input port="stylesheet"> <p:inline> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:template match="/"> <result> <xsl:value-of select="system-property('xsl:product-name')"/> <xsl:value-of select="system-property('xsl:product-version')"/> </result> </xsl:template> </xsl:stylesheet> </p:inline> </p:input> </p:xslt> </p:declare-step> This should output "SAXONEE 9.6.0.7". Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 11/01/16 02:25, David Levy wrote: > I have just started to experiment with XProc. > > Prior to using XProc, I have been transforming XML with XSLT and the > transformation scenario lets me select among a number of transformation > engines such as various flavors of Saxon. When I run the transformation > under XProc as a p:xslt step, I am getting some errors that didn’t > appear with Saxon. These are easily solved, but I wonder: > > (1)What XSLT engine is being used with XProc? Does Calabash provide its > own engine? > > (2)Can I control which engine is being used within XProc? > > With thanks, > > David > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user >

1 0

Re: [oXygen-user] XSLT Processor under XProc
by Oxygen XML Editor Support (Adrian Buza) 11 Jan '16

11 Jan '16

Hello David, > When I run the transformation under XProc as a p:xslt step, I am > getting some errors that didn’t appear with Saxon. Try running the same transformation in Oxygen with Saxon-EE and check if you see the same errors. It's possible that Saxon-EE shows you a different set of errors. > (1)What XSLT engine is being used with XProc? Does Calabash provide > its own engine? XML Calabash (within Oxygen) is configured to use Saxon-EE. A Saxon configuration file is located in Oxygen\lib\xproc\calabash\lib\saxon.config. This can be used to set the edition of Saxon (EE/PE/HE) and various Saxon settings. AFAIK, the command line XML Calabash bundles and uses Saxon-HE, but can probably be configured to use other XSLT engine implementations (Java). > (2)Can I control which engine is being used within XProc? For XML Calabash within Oxygen you can only control the edition of Saxon being used. See the saxon.config file I mentioned above. You can set configuration/@edition="PE" or configuration/@edition="HE". If you're using XML Calabash in the command line (independently from Oxygen) I suspect it's possible to use various javax.xml.transform.TransformerFactory implementations, but don't have a clear configuration path for that. In theory, if the XSLT engine implements the javax.xml.transform.TransformerFactory service, it should also advertise it, so it should work by simply replacing one XSLT engine .jar library with another in the Java classpath. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.2020 Fax: +40-251-461482 On 11.01.2016 02:25, David Levy wrote: > > I have just started to experiment with XProc. > > Prior to using XProc, I have been transforming XML with XSLT and the > transformation scenario lets me select among a number of > transformation engines such as various flavors of Saxon. When I run > the transformation under XProc as a p:xslt step, I am getting some > errors that didn’t appear with Saxon. These are easily solved, but I > wonder: > > (1)What XSLT engine is being used with XProc? Does Calabash provide > its own engine? > > (2)Can I control which engine is being used within XProc? > > With thanks, > > David > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > https://www.oxygenxml.com/mailman/listinfo/oxygen-user

1 0

XSLT Processor under XProc
by David Levy 11 Jan '16

11 Jan '16

I have just started to experiment with XProc. Prior to using XProc, I have been transforming XML with XSLT and the transformation scenario lets me select among a number of transformation engines such as various flavors of Saxon. When I run the transformation under XProc as a p:xslt step, I am getting some errors that didn't appear with Saxon. These are easily solved, but I wonder: (1) What XSLT engine is being used with XProc? Does Calabash provide its own engine? (2) Can I control which engine is being used within XProc? With thanks, David

1 0

Debugger says that watched variable is in "Slot -1"
by Gioele Barabucci 03 Jan '16

03 Jan '16

Hello, while debugging an XSLT function, I added a watch on the parameter `$origin` and another on `string($origin//key)`. The former works flawlessly, the latter always displays the following error: > Error: Local variable $origin uses slot -1 but only 3 slots > are allocated on the stack frame I get this error when the debugger stops at the breakpoint I have placed on the `xsl:if` instruction of the following function: <xsl:function name="f:siblings-until"> <xsl:param name="origin" as="element()"/> <xsl:param name="stopper" as="xs:QName"/> <xsl:variable name="next-sibling" select="$origin/following-sibling::*[1]"/> <xsl:variable name="is-stopper" as="xs:boolean" select="node-name($origin) eq $stopper"/> <xsl:variable name="is-last" as="xs:boolean" select="not($next-sibling)"/> <xsl:if test="not($is-stopper) and not($is-last)"> <xsl:sequence select="$origin, f:siblings-until($next-sibling, $stopper)"/> </xsl:if> </xsl:function> Regards, -- Gioele Barabucci <gioele(a)svario.it>

1 0

Using a different (minor) version of Saxon with oXygen?
by Gioele Barabucci 24 Dec '15

24 Dec '15

Hello, I would like to use Saxon 9.6.0.8 with oXygen 17.1. However, oXygen 17.1 ships with Saxon 9.6.0.7. How can I suggest (or force) oXygen to use a different Saxon JAR? Being limited to Saxon-HE is OK for me, dirty hack are OK as well. Version 9.6.0.8 contains a fix for a very particular bug that I encountered and reported. Without that fix some transformations I am working on take days to complete instead of minutes. Regards, -- Gioele Barabucci <gioele(a)svario.it>

2 3

Parameter substitution in global grouped SQF fixes
by Amanda Galtman 23 Dec '15

23 Dec '15

Hi, I've read in the Schematron Quick Fixes spec that a fix definition or fix group can be global inside <sqf:fixes> or it can be local inside a given Schematron <rule> element. I am seeing cases where a fix group with an abstract parameter works as expected when the fix is inside <rule>, but the parameter substitution does not happen when the fix is inside <sqf:fixes>. The Schematron part of the substitution works as expected, so the problem seems restricted to the quick-fix. The substitution also works when I don't group fixes inside <sqf:group>. The April 2015 draft of the SQF spec says "To be done" in the "Variables and parameter" section. I am not sure whether I'm doing something wrong, or whether the implementation is incomplete. I'm hoping someone on the list knows more. Here's a simple test case that you can put inside the DocBook 5.0 RelaxNG schema. (The "s" namespace is http://purl.oclc.org/dsdl/schematron and I also had to add the sqf namespace definition.) <sqf:fixes> <sqf:group id="testfix"> <sqf:fix id="testfix1"> <sqf:param name="expectedrolevalue" abstract="true"/> <sqf:description> <sqf:title>Set role=$expectedrolevalue</sqf:title> <sqf:p>Set the role attribute to the value '$expectedrolevalue'.</sqf:p> </sqf:description> <sqf:add node-type="attribute" target="role">$expectedrolevalue</sqf:add> </sqf:fix> </sqf:group> </sqf:fixes> <s:pattern abstract="true" id="testcase_ABSTRACT"> <s:rule context="db:para/db:$childname"> <s:assert test="@role='$expectedrolevalue'" sqf:fix="testfix">Expected role attribute to be set to $expectedrolevalue.</s:assert> </s:rule> </s:pattern> <s:pattern is-a="testcase_ABSTRACT"> <s:param name="childname" value="literal"/> <s:param name="expectedrolevalue" value="blah"/> </s:pattern> The quick fix doesn't properly substitute "blah" for $expectedrolevalue. But it does if you either remove <sqf:group> and change id="testfix1" to id="testfix", OR move the entire <sqf:group> element into <s:rule>. Thanks, Amanda

2 2

XML Catalog puzzle
by Gary Gapinski 22 Dec '15

22 Dec '15

2 2